Revision: arch--lord--1.0--patch-28
Archive: lord@regexps.com--2002
Creator: Tom Lord <lord@regexps.com>
Date: Fri Jan 11 19:49:54 PST 2002
Standard-date: 2002-01-11
Summary: ARCHIVE FORMAT: log file format change
Keywords: 
New-files: {arch}/arch/arch--lord/arch--lord--1.0/lord@regexps.com--2002/patch-log/patch-28
Modified-files: =TODO ChangeLog
  ChangeLog.d/lord@regexps.com--2002/ChangeLog.lord--1.0
  ChangeLog.d/lord@regexps.com--2002/ChangeLog.lord-doc--1.0
  archive-transactions/import.sh branching-and-merging/tag.sh
  patch-logs/merge-points.sh
New-patches: lord@regexps.com--2002/arch--lord--1.0--patch-28

I screwed up the `New-patches:' header, as revealed during recent
merge activity.

`New-patches:' should list all patches that are new to the branch
being committed.  `commit' already did this, but:

  `import': didn't include its own log message.  Somehow there *is* an
            entry in 20001Q4/arch--devo, but not others.  Probably
	    a side effect of the last time I "rescued" the base-0
	    revisions.

  `tag': included *only* its own log message.


After that's fixed, `merge-points' no longer needs to recurse on
continuation revisions, which is both a speed-up, and a significant
robustness improvment (since `merge-points' doesn't have to connect to
every archive that has ever contributed a patch!).

Fortunately, fixing `base-0' revisions ex post facto is easy enough.

